1.5.91: scene backdrops, transcript views, stages that rehearse and record - #139

…s/paletteColor: useSpecColor over primer-addons' useColorPalette, which every released primer-addons has), not by usePaletteColor, which no released primer-addons exports yet: the TypeScript build was red (TS2305). A palette name is the palette's value, read by name; a hex is itself; anything else, and a hue a released palette does not have yet, is nothing, so the backdrop draws its own colour. It gives way to usePaletteColor once primer-addons is released and the range raised

….139: usePaletteColor and resolvePaletteColor in place of the local resolver; the specs regenerated, every colour a name

…a glowing circle in its own colour and nothing more, a system a smaller dimmer circle, thin lines with the light that flows along them (space's luminousEdges, without their words), a dark ground in both modes; a click on the circle keeps its details (figureKeeps, aria-expanded on the figure). On every backdrop a member's details open in a card on hover or focus of its figure or name and are kept by a click on its name (aria-expanded, Escape and a second click close it); the figure's click stays its balloon's where a backdrop has one; a system's card peeks on hover everywhere; an open card's node stands over the others

…layer's orb, the design library's SvgAvatarOrb in its theme tone, its three colours the member's own (usePaletteColor; as it is, lighter, deeper), the theme's when it has none; its name and where it runs under it, its details' card on hover and a click as on every backdrop; luminous lines with their words, as on space. The orb is loaded when first drawn, through orbCharacters' lazy SvgAvatarOrb (now exported): @datalayer/design was already a dependency, and no other backdrop loads it. A face carries the member's colour

…ls on every backdrop; agentspecs 0.0.140 and the specs regenerated (the coding agent's recording)

…epository an application is lent, as the harness's workspace holds it now: its URL and pinned revision, HEAD, whether HEAD is that revision, and the lines of git status --porcelain, never a file's contents; shown as the computer is (a deployment's to its owner and its application's editors, as ai-agents answers; nobody it acts for); 404 when it is lent none, 409 when the workspace is no checkout — what the nightly stage rehearsal reads to know the coding agent left README.md as it was lent

…er A2A on its workspace

…te among a deployment's runtime's own

…heme's accent

…ect Object]

… draft 0.3 no longer reserves (the schema line follows agentspecs)

…o network by default, an environment of what was handed in, no capability, bounded files, CPU, memory and time; a kernel that refuses isolation refuses the run

…lan, execute, normalize_result), each adapter versioned on its own; capabilities native, framework-run or unsupported; a source kept by digest and unpacked read-only; a runtime's host and routes; secrets by name, their values taken out of what comes back; the fake adapter that proves it

…that source, and what a framework left that cannot be read is the task's failure

…e sandbox with no sample run; solvers, tools, scorers, metrics and models classified; one sample per trial through inspect_ai.eval with the launch's pool the only scheduler; the eval log kept whole; every scorer on the task and no aggregate nobody chose; a tool runs only if the launch approved it, by an Inspect approval policy; proved identical to a local pinned run on Inspect's mock model

… working directory

…ession is a random sid sent as the Session header, the account's access token kept beside it, every operation asked of the person through the SDK and approved by a message in its conversation, an opaque revision, and other terms another operation

…r pap_confirm is made, ask_the_person is gone, company_standing_permission and user_approval_required are removed from the builders and the operation's spec, and an operation names its tool

…y-example spec itself, CI having no agentspecs clone; the changelog says what 1.6.4 and 1.6.5 carry

…waits for PyPI's index; what 1.6.5 carries

…try carries {target, started_at, ended_at, seconds, microvm_started_at}: when the invocation arrived, when its run ended, the wall time between, and when the runtime's process started

…ried by generate_ops.py (decisionModel in TypeScript), on BattleContestantSpec in the Python and TypeScript types; battles regenerated from agentspecs 0.0.172 (feat/apps-next): in pong and invaders, Red is played by Jev (cloudflare:wrk/typesafe/jev)

… HTTPS with the token, SigV4's refusal said; the CLI sends a prompt so the session keeps its turns

…oAgentSkillSpec), so an agent's page can show each skill's mark

…ts (agentspecs 0.0.170-0.0.171), cogs' identities, Pong's Red played by Jev; the sandbox scaffold writes identity: datalayer-acting-agent, which the specs now require

… SS05)

…on a person's own machine with their DATALAYER_API_KEY remembers on Datalayer (DatalayerMemory, through the runtimes service's memories: the same memories as on a Datalayer runtime, the datalayer-memory skills included); an MCP server without its credentials no longer holds an agent back in the picker, listed in red; a versioned env var reference (NAME:0.0.1) read by its name in the picker and in codemode's server env

…came last — the Studio's AG-UI turns (relayed by ai-agents) then a loop prompt on the same session carry them; with loop agentcore invoke --bearer, the Marketer in the loop picker, a local agent's mem0 memories on Datalayer with DATALAYER_API_KEY, the skills' marks and TAVILY_API_KEY's link

…in the Python and TypeScript types, carried by generate_mcp_servers.py and generate_skills.py (checked, a sentence when malformed), regenerated from agentspecs 4382a36; ${VAR:-default} in an MCP server's args and env (Bluesky's server where BLUESKY_MCP_SERVER_DIR says, else /opt/mcp-servers); PolicySpec carries dogwood, rate_limits and firewall (build:lib refused the Dogwood example policies); the ready line says Jupyter Code Sandbox; a remote server names its headers or its auth

….env_expansion) wherever a server is started — the lifecycle manager, Codemode's registry, the agent factory, codemode's rebuild; Codemode handed Bluesky's ${BLUESKY_MCP_SERVER_DIR:-…} path to node unexpanded

…T_UID) runs the deployment's agent, made at the first invocation as a kept runtime's is (kept_payload, from what ai-agents answers the caller), each invocation through the application's session routes: the session opened by its first run, resumed from its record on a new microVM, recorded under the deployment where it runs ({kind: agentcore, arn}); the contract's routes answered while a deployment is served

…loyment's agent and records its sessions under the deployment, resumed from the record on a new microVM; the release build's policy types (1.6.10 was not published)

…AM's binding page as the return URL and a state IAM issued to the person (identity.consent: kept per person and runtime while it stands, forgotten once used, refused in a sentence without IAM in the path), so IAM binds the consent to who is signed in; the github-repositories tool (the person's repositories with the provider's token, never GITHUB_TOKEN), on the Marketer from agentspecs 64af336